-
Notifications
You must be signed in to change notification settings - Fork 0
update(pkgs): Update geth, nethermind, nimbus, web3signer and mev-boost packages #43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
MartinNikov
commented
Feb 20, 2025
- nethermind: 1.30.3 > 1.31.0
- geth: 1.15.0 > 1.15.2
- mev-boost: 1.8 > 1.9-rc2
- web3signer: 24.6.0 > 25.2.0
- nimbus: 25.1.0 > 25.2.0
Co-authored-by: Kamen Mladenov <[email protected]>
jakubgs
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see no issues with this PR but have not tested it.
|
There is an incorrect hash for |
ca5d270 to
47d047f
Compare
|
Thanks for your Pull Request! This comment will be updated automatically with the status of each package. |
That's odd as I got I'll try the same with fake hash to see if I get |
|
Okay, I've reproduced the hash by using the fakeHash approach: I've then compared the outputs of the 2 fixed-output-derivation expressions: Diffing the individual files shows that these obtained via have Unix line endings (LF), while these obtained via: pkgs.fetchFromGitHub {
owner = "status-im";
repo = "nimbus-eth2";
rev = "v25.2.0";
hash = "sha256-INALxgkuZ4kT/DrpzMBqgNeM8Ar78BRccmGWtqoGhB0";
fetchSubmodules = true;
}have Windows line endings CRLF. |

